-
Notifications
You must be signed in to change notification settings - Fork 650
[Backend Tester] Add nightly CI job for XNNPACK #13390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# We need the runner to test the built library. | ||
PYTHON_EXECUTABLE=python .ci/scripts/setup-linux.sh --build-tool cmake --build-mode Release | ||
|
||
python -m executorch.backends.test.suite.runner $SUITE --flow $FLOW --report "$ARTIFACT_DIR/test_results.csv" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add date, $SUITE, $FLOW specifier in the filename for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion. I'll stack this on top when I add the markdown job summary + pretty printing.
Noting that all CI job failures appear to match failures in the HUD. CI is pretty red, but I've gone through and attempted to ensure that all failures are pre-existing. |
Set up a nightly CI job to run the backend model and operator tests for xnnpack (unquantized and static int8 per channel). This is the first step in setting up continuous coverage using the new suite. I've chosen nightly as the initial run cadence as some of the larger test suites are very long. In the medium-term, I'd like to run a subset of these tests on pull or trunk, but we can start with this.